Triple
T38612716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLE |
E934523
|
entity |
| Predicate | becameProminent |
P24496
|
FINISHED |
| Object | early 21st century |
—
|
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: early 21st century | Statement: [MLE, becameProminent, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameProminent Context triple: [MLE, becameProminent, early 21st century]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
C.
gainedProminenceUnder
Indicates that an entity rose to greater importance, influence, or recognition during the leadership, authority, or period associated with another entity.
-
D.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
E.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.