Triple
T36956626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Brigade |
E914204
|
entity |
| Predicate | supportsMatchmaking |
P99989
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Iron Brigade, supportsMatchmaking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMatchmaking Context triple: [Iron Brigade, supportsMatchmaking, true]
-
A.
hasMatchmakingSystem
chosen
Indicates that an entity includes or is associated with a system that pairs or connects participants based on defined criteria.
-
B.
supportsMatching
Indicates that one entity provides assistance, resources, or functionality that aligns with or complements another entity’s specific requirements or characteristics.
-
C.
matchmakingAuthority
Indicates that an entity has the recognized power or responsibility to arrange, approve, or oversee matches or pairings between other entities.
-
D.
supportsOnlineMultiplayer
Indicates that the subject provides functionality for multiple users to play together over an online network.
-
E.
matchmaker
Indicates that one entity facilitates or arranges a romantic or marital relationship between two other entities.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.