Triple
T11669638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Legion |
E277343
|
entity |
| Predicate | teamCharacteristic |
P79007
|
FINISHED |
| Object | composed of lesser-known heroes |
—
|
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: composed of lesser-known heroes | Statement: [Liberty Legion, teamCharacteristic, composed of lesser-known heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCharacteristic Context triple: [Liberty Legion, teamCharacteristic, composed of lesser-known heroes]
-
A.
squadCharacteristic
chosen
Indicates that a particular characteristic, trait, or property is attributed to a squad as a whole.
-
B.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
-
C.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
D.
teamSpecialty
Indicates the particular area of expertise or focus that characterizes a team’s skills or activities.
-
E.
teamAchievement
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a440d8a481909a13c97813408bc8 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.