Triple
T8639789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludlum Entertainment |
E204615
|
entity |
| Predicate | sourceFranchiseOwner |
P34575
|
FINISHED |
| Object | Robert Ludlum estate |
—
|
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: Robert Ludlum estate | Statement: [Ludlum Entertainment, sourceFranchiseOwner, Robert Ludlum estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceFranchiseOwner Context triple: [Ludlum Entertainment, sourceFranchiseOwner, Robert Ludlum estate]
-
A.
franchiseOwner
chosen
Indicates that one entity holds the ownership and operating rights of a franchise granted by another entity.
-
B.
ownsMajorFranchiseIn
Indicates that an entity has controlling or primary ownership of a major franchise operating within a specified location or jurisdiction.
-
C.
stadiumOwner
Indicates that one entity owns or holds legal possession of a stadium associated with another entity.
-
D.
teamOwner
Indicates that one entity holds ownership or controlling stake over a team.
-
E.
associatedFranchise
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.