Triple
T24887742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Dons |
E622903
|
entity |
| Predicate | sharedMarketWith |
P4377
|
FINISHED |
| Object | Los Angeles Rams |
—
|
NE NERFINISHED |
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: Los Angeles Rams | Statement: [Los Angeles Dons, sharedMarketWith, Los Angeles Rams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedMarketWith Context triple: [Los Angeles Dons, sharedMarketWith, Los Angeles Rams]
-
A.
sharesMarketWith
chosen
Indicates that two entities operate in or target the same market or customer segment, implying competitive or overlapping commercial presence.
-
B.
sharedListingWith
Indicates that one entity has made a listing (such as an item, property, or resource) available jointly or in common with another entity.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:25 a.m.