Triple
T36870519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4-sphere S^4 |
E911210
|
entity |
| Predicate | admitsRoundMetric |
P186615
|
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: [4-sphere S^4, admitsRoundMetric, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admitsRoundMetric Context triple: [4-sphere S^4, admitsRoundMetric, true]
-
A.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
B.
furtherAdmissionRounds
Indicates that additional rounds of admission or selection processes are conducted beyond the initial round.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
E.
includedRound
Indicates that a particular round is part of, or contained within, a larger set, sequence, or event of rounds.
- F. None of above. chosen
Provenance (4 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.