Triple
T15069755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albertosaurus |
E379843
|
entity |
| Predicate | possibleBehavior |
P98589
|
FINISHED |
| Object | pack or group hunting (hypothesized) |
—
|
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: pack or group hunting (hypothesized) | Statement: [Albertosaurus, possibleBehavior, pack or group hunting (hypothesized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleBehavior Context triple: [Albertosaurus, possibleBehavior, pack or group hunting (hypothesized)]
-
A.
possibleJudgment
Indicates a potential or anticipated judgment, decision, or evaluative outcome that could be made about an entity or situation.
-
B.
likelySocialBehavior
chosen
Indicates that an entity is expected or predicted to engage in a particular social behavior or interaction.
-
C.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
D.
possibleSideEffect
Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
-
E.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7f86df48190b3a2cf441fefb477 |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.