Triple
T25886822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baylie Cregut |
E652210
|
entity |
| Predicate | sharesNotableRoleWith |
P35254
|
FINISHED |
| Object | Rylie Cregut |
—
|
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: Rylie Cregut | Statement: [Baylie Cregut, sharesNotableRoleWith, Rylie Cregut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNotableRoleWith Context triple: [Baylie Cregut, sharesNotableRoleWith, Rylie Cregut]
-
A.
sharesRoleWith
chosen
Indicates that two entities hold the same role or position within a given context or system.
-
B.
sharesNotableAssociationWith
Indicates a mutual, noteworthy connection or linkage between two entities that is significant enough to be recognized or highlighted.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesNotabilityWith
Indicates that two entities are notable or recognized for the same or closely related reason, characteristic, or achievement.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 22, 2026, 8:18 a.m.