Triple
T32128563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Collins |
E820575
|
entity |
| Predicate | hasCollaborativeCareer |
P198482
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Larry Collins, hasCollaborativeCareer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborativeCareer Context triple: [Larry Collins, hasCollaborativeCareer, true]
-
A.
hasCollaborativeCareerWith
chosen
Indicates that two entities have engaged in a shared or joint professional activity or career over a period of time.
-
B.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
hasCollaborationIn
Indicates that two or more entities work together or jointly participate in a specific project, context, or domain.
-
D.
hasNotableCollaborationInField
Indicates a collaborative relationship between entities that is recognized as particularly significant or influential within a specific field or domain.
-
E.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: May 1, 2026, 12:29 a.m.