Triple
T11075767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmon Group |
E261860
|
entity |
| Predicate | hasNotableServiceType |
P24034
|
FINISHED |
| Object | railcar leasing |
—
|
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: railcar leasing | Statement: [Marmon Group, hasNotableServiceType, railcar leasing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableServiceType Context triple: [Marmon Group, hasNotableServiceType, railcar leasing]
-
A.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
notableServiceType
chosen
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
E.
hasNotableClientType
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994fcbc081908ff8f7321c0c5892 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.