Triple
T6059362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphaeus |
E134993
|
entity |
| Predicate | hasLimitedBiographicalData |
P44752
|
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: [Alphaeus, hasLimitedBiographicalData, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedBiographicalData Context triple: [Alphaeus, hasLimitedBiographicalData, true]
-
A.
hasUncertainBiographicalDetails
chosen
Indicates that the biographical information about an entity is incomplete, ambiguous, or not reliably established.
-
B.
hasPartInBiography
Indicates that a person or entity is featured or plays a role within someone’s biographical account.
-
C.
hasLimitedRecognition
Indicates that the subject is acknowledged or accepted only to a small extent, in restricted contexts, or by a limited audience.
-
D.
usesBiographicalStructure
Indicates that one entity employs or is organized according to the biographical structure of another entity (e.g., a work structured around a person’s life story).
-
E.
includesBiographiesOf
Indicates that one entity contains or features biographical information about 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570e64408190ae7a2504f63bb58a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.